Skip to content

chore: update dependency eslint to v10#55

Open
renovate[bot] wants to merge 1 commit intomainfrom
renovate/major-eslint
Open

chore: update dependency eslint to v10#55
renovate[bot] wants to merge 1 commit intomainfrom
renovate/major-eslint

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Feb 7, 2026

This PR contains the following updates:

Package Change Age Confidence
eslint (source) ^9.39.3^10.0.0 age confidence

Release Notes

eslint/eslint (eslint)

v10.0.2

Compare Source

v10.0.1

Compare Source

Bug Fixes

Documentation

  • 5b3dbce docs: add AI acknowledgement section to templates (#​20431) (루밀LuMir)
  • 6f23076 docs: toggle nav in no-JS mode (#​20476) (Tanuj Kanti)
  • b69cfb3 docs: Update README (GitHub Actions Bot)

Chores

v10.0.0

Compare Source


Configuration

📅 Schedule: Branch creation - "after 10pm,before 5:00am" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot added the dependencies label Feb 7, 2026
@renovate
Copy link
Contributor Author

renovate bot commented Feb 7, 2026

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: eslint-plugin-bpmn-io@2.2.0
npm ERR! Found: eslint@10.0.2
npm ERR! node_modules/eslint
npm ERR!   dev eslint@"^10.0.0" from the root project
npm ERR!   peer eslint@"^6.0.0 || ^7.0.0 || >=8.0.0" from @eslint-community/eslint-utils@4.9.1
npm ERR!   node_modules/@eslint-community/eslint-utils
npm ERR!     @eslint-community/eslint-utils@"^4.9.1" from @typescript-eslint/utils@8.56.1
npm ERR!     node_modules/@typescript-eslint/utils
npm ERR!       @typescript-eslint/utils@"8.56.1" from @typescript-eslint/eslint-plugin@8.56.1
npm ERR!       node_modules/@typescript-eslint/eslint-plugin
npm ERR!         @typescript-eslint/eslint-plugin@"8.56.1" from typescript-eslint@8.56.1
npm ERR!         node_modules/typescript-eslint
npm ERR!       2 more (@typescript-eslint/type-utils, typescript-eslint)
npm ERR!     @eslint-community/eslint-utils@"^4.8.0" from eslint@10.0.2
npm ERR!   7 more (@typescript-eslint/eslint-plugin, ...)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer eslint@"^9" from eslint-plugin-bpmn-io@2.2.0
npm ERR! node_modules/eslint-plugin-bpmn-io
npm ERR!   dev eslint-plugin-bpmn-io@"^2.2.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: eslint@9.39.3
npm ERR! node_modules/eslint
npm ERR!   peer eslint@"^9" from eslint-plugin-bpmn-io@2.2.0
npm ERR!   node_modules/eslint-plugin-bpmn-io
npm ERR!     dev eslint-plugin-bpmn-io@"^2.2.0" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /runner/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /runner/cache/others/npm/_logs/2026-02-26T07_43_21_444Z-debug-0.log

@renovate renovate bot force-pushed the renovate/major-eslint branch from 5b397fd to 88ae1ca Compare February 26, 2026 07:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants